Remote Server/Remote Connection handling update errors
======================================================

Overview
--------
This sample provides a project group with two applications:
1.  A Remote Server which uses the Bdp RemoteServer and a DataSync to provide
remote data from the Interbase CUSTOMER table.
2.  A Client Application which uses the RemoteConnection and DataHub to retrieve
the data from the Remote Server and populate a Data Grid.  The Client application
then allows the user to handle update errors using the OnUpdateError event
of the DataHub:

  private void dataHub1_OnUpdateError(object sender,
                        Borland.Data.Common.BdpUpdateErrorEventArgs e)
  {
     Borland.Data.Provider.ReconcileErrorForm f = new
                                Borland.Data.Provider.ReconcileErrorForm(e);
     f.ShowDialog();
  }


Setup
-----
        Before working with this sample it will be necessary to set the
        BdpConnection control in the Server application to a valid Interbase
        connection pointing to the standard Interbase employee.gdb, which
        contains the CUSTOMER table.

Running the Application
-----------------------
        First, double click on the RecDrrorWithDataSync.exe project in the
        Project Manager.  Run the application.  Then, double click on the
        DataSyncRecErrorClient.exe, and run that application.  Then run a second
        instance of the application.

        To invoke an error, change any row value for one of the users, and
        hit the "Apply" button.  Then change a value in the same row of the
        second user, and hit "Apply".

        When the error dialog appears, you have a number of options, both
        in terms of how you want to handle the error, and what data you want
        to retain.

        In terms of how you want to handle the error, you can elect to
        retry using the primary key, to ignore the offending row and continue
        on to the next row that contains a change, or abord the update process
        completely.

        In terms of the data to be used, you can elect to use the server data,
        the original data (before it was changed), or the current data.  The
        current data can be changed in the datagrid on the ReoncileError form.

        If you elect to force the update using the primary key, you can verify
        that this has worked by hitting the "Refresh" button for the second
        user.


